Registry verification of item identity for a mechanized store

ABSTRACT

Registry verification is used in a mechanized store. One or more sensors are used to identify one or more items available for purchase at display in a store. One or more cameras are used to detect identities of the one or more items removed by a user from the display. Identities of the one or more items identified by the one or more sensors are compared to the identities of the one or more items detected by the one or more cameras to obtain a result that is saved to a record of the user. The user can be charged for the items removed from the display.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/217,442, filed Dec. 12, 2018, entitled “Registry Verification For AMechanized Store Using Radio Frequency Tags,” which application is acontinuation-in-part application of U.S. patent application Ser. No.15/853,252, filed on Dec. 22, 2017, entitled “Registry Verification ForA Mechanized Store Using Radio Frequency Tags,” now U.S. Pat. No.10,192,408, issued Jan. 29, 2019, which application is a continuation ofU.S. patent application Ser. No. 15/495,555, filed on Apr. 24, 2017,entitled “Registry Verification For A Mechanized Store,” now U.S. Pat.No. 9,886,827, issued Feb. 6, 2018, which application claims the benefitof U.S. Patent Application No. 62/326,931, filed on Apr. 25, 2016, andU.S. Patent Application No. 62/486,665, filed on Apr. 18, 2017. U.S.application Ser. No. 16/217,442 also claims the benefit of U.S. PatentApplication No. 62/612,317, filed on Dec. 29, 2017, entitled“Distributed Ledger For Retail Transactions,” U.S. Patent ApplicationNo. 62/640,018, filed Mar. 15, 2018, entitled “Distributed LedgersProtecting Privacy In Physical Transactions,” U.S. Patent ApplicationNo. 62/696,990, filed Jul. 12, 2018, entitled “Registry Verification ForA Mechanized Micro Market,” and U.S. Patent Application No. 62/776,038,filed on Dec. 6, 2018, entitled “Method and System for a Smart Display.”The disclosures of these applications are hereby incorporated byreference in their entirety for all purposes.

BACKGROUND

This disclosure generally relates to registers. Registers are used torecord and/or verify transactions. Registers include machines andsystems for ascertaining a number of movements of various devices orproducts. Some registers are used to disclose a numerical quantity. Someexamples of registers include cash-registers, fare-registers, votingmachines, and calculators, which have registering or counting elementsand may have additional certain other features for a given purpose.

Traditionally, retail transactions have taken place in a well-definedphysical store with both a representative of the retail store (themerchant) and the shopper (the consumer) present. The consumer typicallypicks specific products from shelves or fridges. At the end of thepicking activity the shopper proceeds to the cash register and pays forthe merchandise in a person-to-person transaction with a storeassociate. Traditionally, the presence of the store associate isnecessary to execute payment and/or to prevent shoppers from stealing.

BRIEF SUMMARY

Store associates are costly, they are difficult to manage, and theyeffectively limit the period of time that the store is open forbusiness. Thus, there is a need in the art for methods and systems forautomatically or semi-automatically operating a retail store. Thepresent disclosure enables the operation of a store where only theshopper is present and/or where the number of store associates isreduced.

The present disclosure relates generally to methods and systems forautonomous and secure physical transactions. More particularly, someembodiments relate to identifying a shopper, providing physical storeaccess to the shopper, identifying the products the shopper removes fromshelves, creating a digital shopping basket corresponding to a physicalshopping basket, and/or automatically or semi-automatically charging theshopper for items in the shopping basket.

In some embodiments, benefits are achieved over conventional techniques.For example, some embodiments provide methods and systems to operate aretail store unattended, to allow shoppers to shop outside normaloperating hours, to operate a store with only a security guard present,to reduce shop lifting and theft, to operate a store without a cashregister, to provide easy access to merchandise for delivery services,and/or to operate stores securely in public or semi-public places, suchas hotels, shopping malls, airports, train stations, sidewalks andpedestrian areas, schools or universities, and on public transportvehicles.

In some embodiments, a system using registry verification for amechanized store with permitted access comprises: a structure enclosingan area, wherein the structure is configured to permit access of aplurality of potential users to the area; one or more displays in thearea; a plurality of items for sale located at the one or more displays,wherein the plurality of items are mapped to a code configured to beread by a scanning device; one or more cameras configured to count anumber of items in a registry removed by a user from the one or moredisplays; and one or more processors. The one or more processors areconfigured to: receive a number of items scanned from the scanningdevice; receive the number of items removed counted by the one or morecameras; compare the number of items scanned to the number of itemsremoved to obtain a compared value (sometimes referred to as a result);and saving the compared value to a record of the user.

In some embodiments, the one or more displays comprises a first displayand a second display; a first item of the plurality of items is locatedat the first display; a second item of the plurality of items is locatedat the second display; the camera is further configured to: record thatthe first item was removed from the first display and record that thesecond item was removed from the second display. In some embodiments,the one or more processors are configured to update a first electronicbasket and a second electronic basket; the first electronic basketcorresponds to the number of items removed by the user; and the secondelectronic basket corresponds to the number of items scanned. In someembodiments, the one or more cameras are configured to count the numberof items without identifying the user; the one or more cameras areconfigured to count the number of items without identifying items; theone or more cameras are configured to count the number of items byidentifying movement of a hand and determining if the hand is holding anitem; the structure is configured to permit only one user at a timeaccess to the area; the area is a volume less than 3.5 meters wide by3.5 meters long by 3.5 meters tall; the area is a volume less than 1.5cubic meters; the structure lacks climate control to control the climateof the area; the system further comprises a Bluetooth receiverconfigured to unlock doors of the structure based on a receivedBluetooth signal; and/or the cameras are configured to use artificialintelligence for determining if an item was taken from a display of theone or more displays.

In some embodiments, a method for using registry verification for amechanized store comprises: permitting a user access to a structureenclosing an area; counting, using one or more cameras, a number ofitems removed from one or more displays by a user; tracking, in aregistry, the number of items removed; receiving a number of itemsscanned by a scanner; comparing the number of items in the registry tothe number of items scanned to obtain a result; and saving the result toa record of the user. In some embodiments, the method further comprisesalerting a store owner, store employee, independent contractor, and/orlaw enforcement based on the compared result being a negative number,such that the number of items removed is greater than the number ofitems scanned; tracking the user in the area; and/or transmitting anindication to the user that the compared result is zero, such that thenumber of items removed equals the number of items scanned. In someembodiments, the scanner is a mobile device belonging to the user and/orcounting the number of items removed from one or more displays by a useris performed without identifying the items removed. In some embodiments,a memory device comprising instructions that when executed cause one ormore processors to perform the method steps.

In some embodiments, a method for determining items removed from adisplay is described. In some embodiments the method comprises one ormore of the steps: creating a video recording of the display using avideo camera directed at the display; analyzing frequency components offrames of the video recording; selecting a plurality of frames of thevideo recording based on the plurality of frames having higher frequencycomponents than other frames in the video recording; subtracting abackground in the plurality of frames; detecting a hand in the pluralityof frames; resolving, in the plurality of frames, if the hand holds anobject; recording state vectors corresponding to the plurality of framesbased on resolving if the hand holds an object in the plurality offrames; and detecting that the object was removed from the display basedon the state vectors and a time sequence of the plurality of frames. Insome embodiments, detecting the hand in the plurality of framescomprises comparing movement in foreground of the plurality of frames todetermine which part of the foreground has more movement than anotherpart of the foreground.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description and specific examples, whileindicating various embodiments, are intended for purposes ofillustration only and are not intended to necessarily limit the scope ofthe disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appendedfigures.

FIG. 1 depicts a block diagram of an embodiment of a system for usingregistry verification for a mechanized store.

FIG. 2 illustrates a flowchart of an embodiment of a process for usingregistry verification for a mechanized store with permitted access.

FIGS. 3A and 3B depict simplified drawings of an embodiment of amechanized store using registry verification.

FIG. 4 depicts a simplified drawing of a shelf unit in a store usingregistry verification.

FIG. 5 depicts a simplified drawing of another embodiment of a structureusing registry verification.

FIG. 6 illustrates a flowchart of an embodiment of a process fordetermining items removed from a display.

FIG. 7 depicts a block diagram of an embodiment of a computer system.

FIG. 8 depicts a block diagram of an embodiment of a special-purposecomputer system.

FIG. 9 depicts an exemplary user database and merchant databaseaccording to one or more embodiments.

FIG. 10 depicts an exemplary decentralized database according to one ormore embodiments.

FIG. 11 illustrates an exemplary process according to one or moreembodiments.

FIG. 12 illustrates an exemplary process according to one or moreembodiments.

FIG. 13 illustrates an exemplary process according to one or moreembodiments.

FIG. 14 illustrates an exemplary process according to one or moreembodiments.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) only,and is not intended to limit the scope, applicability, or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiment(s) will provide those skilled in the art with anenabling description for implementing a preferred exemplary embodiment.It is understood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

Some embodiments relate to methods and systems for operating a store ormarket place where only one party of the transaction is physicallypresent. Some embodiments relate to acquiring imaging data of an objectusing an imaging tool, acquiring imaging data of a person, unlocking aphysical container based on the identity of the person, and/or executinga transaction relative to a specific object or ensemble of objects. Forexample, a traditional retail store can operate unattended with only ashopper is present in the store. In some embodiments, structures, suchas cabinets or physical rooms, function as a micro market where shopperstransact a product purchase in a self-serve fashion.

Referring first to FIG. 1, a block diagram of an embodiment of a system100 for using registry verification for a store 102 is shown. In someembodiments, a user's mobile device 104 is used to interact with thesystem 100. In some embodiments, the system 100 comprises the mobiledevice 104. The mobile device 104 is a computing device small enough tobe held and operated in a hand of the user. A smartphone is an exampleof a mobile device. The mobile device 104 comprises one or more of: adevice display, a wireless transmitter, a wireless receiver, device datastorage, device processing unit, an imaging sensor, an RF sensor, aposition sensor, and/or an authentication system (e.g., a passcode foroperating the mobile device and/or a biometric sensor).

The system comprises the store 102 and a processing unit 106. The store102 comprises an enclosure 108, a display 112, an item 116, a camera120, a transceiver 124, a locking mechanism 128, and/or a scanner 132.The processing unit 106 comprises a store data base 136, a customerdatabase 140, a product database 144, and/or a processor 148. In someembodiments, the processing unit 106 comprises one or more processors148. The one or more processors 148 can be split between one or morelocations. For example, there can be a local processor 148 and a remoteprocessor 148, which are both part of the processing unit 106.

The display 112 is used to present the item 116 for sale. In someembodiments, the display 112 is a shelf. The item 116 comprises a label(e.g., an optical identifier such as a barcode and/or QR code), an RFidentifier, and/or distinctive packaging. The item 116 is mapped to aproduct, description, and/or price by the label, RF identifier, and/ordistinctive packaging.

The camera 120 is used to observe a shopper removing the item 116 fromthe display 112. The locking mechanism 128 is used to permit the shopperaccess to the item 116. The shopper, or a store employee, uses thescanner 132, and/or the mobile device 104, to scan the item 116 (e.g.,to scan the optical identifier attached to or associated with the item116). Of course, the system 100 can comprise a plurality of enclosures108, displays 112, items 116, cameras 120, transceivers 124, lockingmechanisms 128, and or scanners 132.

In some embodiments, the mobile device 104 is used to authenticate ashopper. Authentication can happen using a wireless connection betweenthe mobile device 104 and the transceiver 124. Authentication can happenusing a positioning sensor which associates a location of the shoppernext to, or inside, the enclosure 108 of the store 102. Authenticationcan happen using an image sensor or visual sensor associated with theenclosure 108 (e.g., camera 120) or the mobile device 104.Authentication can also happen using a biometric sensor that isassociated with the store 102 or the mobile device 104.

Upon authentication of the shopper, the shopper is granted physicalaccess to the item 116. The enclosure 108 comprises a door. The door islocked by the locking mechanism 128. In some embodiments, the lockingmechanism 128 includes a wireless lock, a camera enabled lock, a barcodereader enabled lock, and/or a remote-controlled lock. The lockingmechanism 128 could be based on a number of different wireless protocolssuch as Bluetooth, Bluetooth low energy (BLE), Bluetooth Smart, WiFi,Near Field Communication, and/or Radio Frequency IDentification (RFID).

After the shopper has been granted physical access, the shopper removesor adds items 116 from one or more displays 112. A display 112 is alocation where an item for purchase, rent, and/or transfer of ownershipis placed on or near. In some embodiments, the display 112 is a storagelocation. The shopper removes the item 116 from the display 112 in orderto purchase the item. In a case of a store worker or supplier, items 116are placed in and/or on the display 112 for restocking. A user issomeone or something that adds and/or removes items 116 from one or moredisplays 112. Examples of users include shoppers, store workers,contractors, suppliers, and robots. As activities to place and remove anitem 116 from a display 112 occur, one or more cameras 120 record theactivities of the user. The images captured are processed by aprocessing unit 106 (e.g., a local processing unit and/or a remoteprocessing unit; a processing unit can comprise one or more processorsand one or more data storage devices).

In some embodiments, images captured are analyzed to count a number ofitems 116 being removed and/or added to one or more displays 112. At anend of a store visit, the processing unit 106 has a count of how manyitems 116 the user removed or added to one or more displays 112. In someembodiments, the processing unit 106 tracks in a registry the count ofhow many items 116 the user removed or added.

In some embodiments, images captured are analyzed to identify items 116that are being removed or added to the display 112. At the end of thestore visit, the processing unit 106 has an accurate list of which items116 the user removed or added to the one or more displays 112. In someembodiments, images captured are analyzed to identify from which display112, and/or part of a display 112, an item 116 is being removed and onwhich display 112, and/or part of a display 112, an item 116 is beingreplaced. At an end of a store visit, the processing unit 106 has anaccurate list of where items 116 remaining are located in the store(e.g., to alert a store employee to put an item 116 back where itbelongs).

Identification of an item 116 is accomplished using one or any of thefollowing mechanisms: an image sensor collocated with a user's personalmobile device 104, a camera 120 or cameras 120 installed in the store102 location, optical barcode scanning software, radio frequencyidentification, machine learning technology such as recognition softwareusing a neural network, and/or water marking on the product's packaging.In some embodiments, images are being analyzed using reinforcementlearning, convolutional neural networks, image segmentation, adversarialnetworks, residual learning, residual networks, and/or optical flowanalysis.

In some embodiments, a record of items 116 is assembled in a digitalshopping cart by algorithms based on visual imagery of the items 116. Insome embodiments, a record of items 116 is assembled in the digitalshopping cart through a use of RFID tag readers sensing a removal ofRFID-enabled items 116 from the display 112. In some embodiments, theuser assembles a record of items 116 in the digital shopping cart byscanning the items 116 with a mobile device 104. In some embodiments,the user assembles a record of items 116 in the digital shopping cart byscanning individual items 116 with the scanner 132 collocated with thedisplay 112 and/or in another part of the store 102.

Upon completion of the shopping activity, payment is executed based onthe items 116 in the digital shopping cart of the shopper. Payment canbe triggered by a number of different events, including the shopperleaving the store 102, the location of the shopper being sensed outsidethe physical store 102, the shopper scanning her mobile device 104 at anexit point (e.g., at the door), the shopper passing a beacon tag, theshopper pushing a button, the shopper talking into a microphone, etc.

In some embodiments, two digital baskets are used: a first digitalbasket and a second digital basket. The first basket is a record of whatthe shopper presents for purchase (e.g., what is scanned for purchase).For example, the shopper uses her mobile device 104 to scan a bar codefor each item 116 the shopper intends to purchase; and/or the shopperuses a barcode reader at a location (e.g., near a front of the store102; or near the door). The barcode, or other identifying technology,may be collocated with the items 116 and/or with the display 112. Thesecond digital basket comprises a count of items removed or added by theuser (e.g., as counted using cameras 120). The processing unit 106counts how many items 116 the shopper has removed or added to one ormore displays 112, independently of how many items 116 the shopperpresents for checkout. As the shopper creates a physical shopping basketcontaining physical product, the processing unit 106 keeps track of acount of products in the second digital basket by visually tracking theactivities of the shopper in the store 102.

After the shopper presents her items 116 for check out, the processingunit 106 compares the count of items 116 in the first digital basket tothe count of items 116 in the second digital basket. If the count ishigher in the first digital basket than in the second digital basket,the processing unit 106 may transmit a message to the shopper to verifyand make sure that she is not paying for too many products. On the otherhand, if the count in the first digital basket is lower compared to thesecond digital basket, the system may ask the shopper to verify and makesure that she is not taking more product with her than she is payingfor. In the case of behavior that suggests fraud, the system can alsotake more drastic measures such as asking a store representative tointervene with the shopper before and/or after she leaves the store. Inan extreme case, the system may inform law enforcement directly and/oras quickly as possible.

In some embodiments, counting items 116 for the second digital basket isaccomplished with a number of possible methods and/or combinationsthereof. For example, a sequence of images of the shopper are analyzed.Individual frames are analyzed to determine if a hand handling an item116 is present in the frame. If an item 116 is detected in the hand,previous and subsequent frames are analyzed to determine if the item 116was removed or added to the display. Accordingly, a count of the seconddigital basket is increased or decreased. In some embodiments, sequencesof frames are analyzed by a recurring neural network. In someembodiments, an individual frame, or sequence of frames, is analyzed todetermine if more than one item 116 is handled by the shopper. Thisinformation is used to accurately manipulate the count of the seconddigital basket.

In some embodiments, the enclosure 108 is configured to permit only oneshopper at a time to be in the store 102 and shop. Access to the store102 is controlled through a Bluetooth activated automatic entry door.Cameras 120 are installed (e.g., in a ceiling) for the purpose ofmonitoring the shopping activity.

In some embodiments, a shopper is tracked through the store to obtain acomplete count of the shopping activities in the store 102 relative toan individual shopper. Tracking can be done visually using more than onecamera 120, where the system uses visual information about the shoppersuch as an appearance of her clothing, her face, or physical appearance.Tracking can also done by and/or assisted by wireless signals, such asBluetooth beacons, WiFi signals, modulated light, and/or by signalsbased on other wireless or optical protocols. Some of the trackingmechanisms contemplated here rely on the shopper's mobile device 104 aseither the source of the tracking signal and/or a recipient of atracking signal.

Referring next to FIG. 2, a flowchart of an embodiment of a process 200for using registry verification for a mechanized store is illustrated.Process 200 begins in step 204 with permitting access to a structure(e.g., the enclosure 108). The structure encloses an area. In someembodiments, “area” generally means a designated space, such as avolume, unless indicated to the contrary. In some embodiments, thestructure is large enough that the user walks into the structure. Insome embodiments, the structure is or resembles a traditional retailstore. In some embodiments, permitting access allows a user to reachinto the structure (e.g., for a store display, such as a fridge, or forvending on public transportation). In some embodiments, permittingaccess comprises receiving a signal (e.g., a radio frequency signaland/or optical signal). In some embodiments, the signal is transmittedfrom a mobile device 104 of a shopper. A lock is unlocked, based onreceiving the signal. In some embodiments, the signal comprises a codeand the code is authenticated.

In step 208, a number of items 116 removed from one or more displays 112are counted. One or more cameras 120 are used to count the number ofitems 116 removed. For example, the one or more cameras 120 record ashopper removing items 116 from a shelf. Video images are analyzed todetermine that an item 116 was removed. In optional step 212, the one ormore cameras 120 are used to count items 116 that are returned to one ormore displays 112.

In step 216 the number of items 116 removed are tracked in a registry.The registry receives a +1 for an item 116 counted as removed from adisplay 112 and a −1 for an item 116 that is returned to a display 112.In some embodiments, the register comprises an integer value (e.g., avalue of the number of items 116 removed). In some embodiments, theregister tracks only one value, the integer value. In some embodiments,the register tracks further details about an item 116 removed, such as adisplay 112 that the item 116 was removed from and/or an identificationof the item 116 (e.g., a soda can).

In step 220, a number of items 116 scanned by a scanner 132 and/or themobile device 104 are received by the processing unit 106. In someembodiments, the scanner 132 is affixed in the store 102 (e.g., next toa display 112, and/or the item 116 is held up to a camera 120 and thecamera reads a label on the item 116, in addition to counting that theitem 116 was removed from the display 112). In some embodiments, thescanner 132 identifies each item 116 and transmits a list of the items116 scanned. And the number of items 116 scanned is received by countingitems on the list.

In step 224, the number of items 116 removed, which is tracked by theregistry, is compared to the number of items 116 scanned to obtain aresult. The result is saved to a record of the user. For example, thenumber of items 116 removed is 7 and the number of items 116 scanned is7. Thus the result is zero, and the result, which is a good result, issaved to the record of the user.

In step 228, the user is allowed to check out if the result is zero. Insome embodiments, if the result is zero, then an indication is sent tothe user that the number of items 116 removed matches the number ofitems 116 scanned.

In optional step 230, an error report is transmitted. In someembodiments, if the result is non-zero an error report is transmitted.For example, if the result is less than zero, then the user is notifiedthat she might have scanned an item 116 more than once. If the result isgreater than zero, then the user is notified to check her items 116 tosee if one or more items 116 have not been scanned. In some embodiments,if the result is greater than zero then a store employee receives theerror report. In some embodiments, a user is allowed to check out eventhough the result is non-zero.

In some embodiment, before a shopper enters a store, at a time theshopper enters the store 102, and/or before the shopper removes an item116, the processing unit 106 ranks the shopper on a scale oftrustworthiness so that the processing unit 106 can predict how likelythe shopper is to commit fraudulent activity. Before the shopper leavesthe store 102, the processing unit 106 has evidence of potential wrongdoing by the shopper on the shopper's particular shopping trip. Video,recorded by the cameras 120, can be reviewed to verify fraudulentactivity or to confirm trustworthy behavior by a shopper (e.g., after astore employee receives the error report in step 230).

In an example implementation, the store first encourages the shopper tosign up for an account with the system using her smartphone. The shopperuses her smartphone to scan a code attached to the outside wall of thestore which takes her to a website. The shopper is now able to downloadthe system's smartphone app. The shopper starts the app and then entersher name, address, and phone number. She also enters credit card or bankaccount credentials. The system checks the validity of the shopper'scredentials and determines how much credit is available on the creditcard and/or in the bank account. If the credit is above a certainthreshold, the shopper's account is activated and immediately availablefor use.

In the example implementation, the shopper then pushes a ‘door open’button on the app. This causes the shopper's smart phone to emit anencrypted Bluetooth beacon signal. The signal is received by theBluetooth receiver connected to the door locking mechanism 128. Uponreceiving the authenticated beacon signal, the receiver causes the doorto unlock and open. The shopper enters and the door closes behind her.The system then formally opens the shopping session tied to the accountof the shopper. There are three “shopping baskets” as part of thesystem: basket 1 (B1), basket 2 (B2), and basket 3 (B3).

Basket 1 (B1) reflects the physical basket of products the shopper hasremoved from the product display area. B1 is described by N1, the numberof items in basket B1, and P1, the vector containing the identifiers ofall the product p1_i located in B1. The term basket is used as anabstract description for products removed from the display(s). B1 may infact be a shopping basket, or it may be a bag or container brought alongby the shopper, or it may be the location of the shopper's pantspockets.

Basket 2 (B2) reflects the first digital basket of products the shopperhas scanned for purpose of checking out items. B2 is described by N2,the number of items in basket B2, and P2, the vector containing theidentifiers of all the product p2_i located in B2. The shopper createsP2 by physically scanning an optical code on products (the barcode) withher smart phone using an imager of the smart phone. As a default, eachtime a code is scanned, the corresponding product is added to the firstdigital shopping basket and N2 is increased by one. The smartphonedisplay provides feedback to the shopper as to which products have beenscanned so far. If a shopper makes a mistake, or decides to put aproduct back on the shelf, she can adjust the list P2 using thetouchscreen on the smartphone. In another mode, the shopper can scan abarcode to remove the product from the list instead of adding it.

Basket 3 (B3) reflects the activities of the shopper as observed andestimated by the camera system. B3 is described by N3, the estimatednumber of items in basket B1, and P3, the vector containing theestimated identifiers of all the product p3_i located in B1. As soon asthe shopping sessions starts, the system constantly updated andestimates B3 based on the set of sensor information available to thesystem (e.g., images and frames transmitted from cameras installed inthe store and/or RF reads from RF readers).

In the example implementation, the shopper is instructed to pick anitem, one by one, scan it with her mobile phone (the mobile phone beingconsidered a scanner), and place it in the shopping basket (B1). If shewants to put a product back after having scanned it, she can hand editthe shopping list to do so. At any time, the shopper can select acheckout option on the mobile phone. After choosing checkout, theshopper leaves the store and the store door locks behind her. Payment isexecuted.

In the example implementation, after the shopper selects checkout, thesystem compares B3 to B2 and/or N3 to N2. The system can draw severalconclusions from the comparison. If N2=N3: The estimated number ofproducts picked (N3) matches the number of product in the digitalshopping basket N2. The system assumes that the transaction was correctand that the shopper paid for everything she took. The transaction iscomplete.

If N2>N3: The estimated number of products picked (N3) is smaller thanthe number in the digital shopping basket. The system provides feedbackto the shopper, asking her to make sure she did not double scan anyitems. The shopper has another opportunity to review her physicalshopping basket (B1) and her digital shopping basket (B2) and make anycorrections if appropriate to B2. Then N3 and N2 are compared once againand payment is executed based on the content of B2.

If N3>N2: The estimated number of products picked (N3) is larger thanthe number in the digital shopping basket. In this case, the systemassumes that the shopper will pay for less product than she intends totake with her. The system can take one or more of the followingmeasures:

-   -   Alert the shopper of a mismatch and ask her to check the first        digital shopping basket (B2).    -   Notify a store manager or law enforcement that fraud may be        underway.    -   Instruct a store associate to examine the shopper's physical        basket (B1).    -   Instruct a person to review the video footage of the shopping        activity.    -   If there is enough evidence of theft (e.g., through video),        charge the shopper's credit card for the items that were not        scanned.    -   Decrease a trust score of the shopper.

B1 and B2 are shopping lists created by the shopper. B1 is createdthrough the physical product picking by the shopper. B2 is created bythe scanning and editing of products on the shopper's smart phone. Incontrast B3 and N3 are created by the system. They system estimates asaccurately as possible B1 and/or N1.

FIGS. 3A and 3B depict simplified drawings of an embodiment of amechanized store 300, which uses registry verification. FIG. 3A is aperspective view. FIG. 3B is a top view with a roof 304 of themechanized store 300 removed to show further details. The mechanizedstore 300 comprises a structure (enclosure 108) enclosing an area, oneor more displays 112, a plurality of items 116, cameras 120, atransceiver 124, a locking mechanism 128, and a processing unit 106.

The structure comprises the roof 304 and doors 306. Items 116 for saleare on displays 112. There is a first display 112-1 and a second display112-2. The cameras 120 track a number of items 116 removed or added toeach display 112.

In some embodiments, the structure is configured to permit only one userat a time access to the area and/or only one user is observed in a smallarea at a time. In some embodiments, the area is a volume less than 3.5meters wide by 3.5 meters long by 3.5 meters tall. In some embodiments,the area is less than 1.5 cubic meters (e.g., vending described in FIG.5 below). In some embodiments, the structure lacks climate control tocontrol a climate of the area (though a display 112 may have climatecontrol for items in the display 112, such as cooling a beverage). Insome embodiments, the structure is lightweight (e.g., as opposed to aconcrete structure) and/or has an upscale feel (e.g., so that thestructure can be placed at a pedestrian location of a city). A structureallowing only a single-shopper, sometimes referred to as a walk-invending machine, reduces complexity of computer algorithms and/or anumber of cameras 120 as compared to a structure that permits multipleshoppers at one time. In some embodiments, a shopper doesn't have to betracked, just observed in a small area, reducing complexity of computeralgorithms.

FIG. 4 depicts a simplified drawing of a shelf unit 400 in a store 102using registry verification. Cameras 120 are mounted on the shelf unit400. Items 116 for sale are on the shelf unit 400. Not all items 116 arelabeled in FIG. 4 for simplicity. A processing unit 106 is mounted onthe shelf unit 400. The cameras 120 observe a shopper removing items116. In some embodiments, the scanner 132 is integrated with theprocessing unit 106 so that a shopper can scan items 116 at theprocessing unit 106. In some embodiments, a transceiver 124, a camera120, and/or a locking mechanism 128 is integrated with the processingunit 106. In some embodiments, the shelf unit 400 is part of amechanized store.

FIG. 5 depicts a simplified drawing of another embodiment of a structureusing registry verification. In some embodiments, the structureenclosing the area is a cabinet and/or a micro market with one or morecameras 120. In FIG. 5 a first display 112-1, a second display 112-2,and a third display 112-3 are shown. Each display 112 in FIG. 5 is astructure and each comprises a door 306, a camera 120, and a processingunit 106. Not every feature is labeled for simplicity to not crowd thefigure. A transceiver 124 is integrated with the processing unit 106. Alocking mechanism 128 locks and unlocks the door 306. For example, theshopper uses his mobile device 104 to unlock a door 306. The shopperthen pockets his mobile device 104. The shopper removes an item 116 froma display 112. The shopper scans the item 116 using a scanner 132integrated with the processing unit 106. A screen on the display 112shows the shopper what items 116 are in the second basket (B2; the firstdigital basket). The screen is a digital and/or electronic display. Thefirst digital basket is also transmitted to the mobile device 104. Theshopper has the option to read the screen on the display 112 and/or onthe mobile device 104. The camera 120 counts items 116 removed andupdates the second digital basket. In some embodiments, the seconddigital basket is reflected in the screen on the display 112 and/or onthe mobile device 104. In some embodiments, the camera 120 alsodetermines what the item 116 removed is, in addition to counting thenumber of items 116 removed. In some embodiments, the display 112 inFIG. 5 is a mechanized store.

FIG. 6 illustrates a flowchart of an embodiment of a process 600 fordetermining items removed from a display. In some embodiments, N3 iscalculated based on determining items removed from the display. Process600 begins in step 604, with obtaining a video of a display. A camera(e.g., a video camera) is mounted in the store. The camera, which isdirected at the display so that the display is in a field of view of thecamera, creates a video of the display. In some embodiments, two or morecameras are used to create video of one or more displays. In someembodiments, the video is recorded. In some embodiments, the video isstreamed. In some embodiments, a processor at the structure analyzes thevideo. In some embodiments video is saved and/or streamed to a remotelocation from the structure for current and/or later viewing and/oranalysis.

In step 608, frequency components of frames of the video are analyzed.In some embodiments, a certain number of frames are grouped together tobe analyzed. For example, 15, 30, 60, or 90 frames are analyzedtogether. Each frame is given a score corresponding to how high or lowthe frequency components are of the frame.

In step 612, a plurality of frames with higher frequency components areselected. Higher frequency components generally correspond to sharperimages. Thus, frames with lower frequency components are more likely tohave blurred images.

In step 616, a hand is detected in the plurality of frames of the video.In some embodiments, a hand is detected by analyzing pixels that changefrom frame to frame more than other pixels. For example, a background issubtracted based on a baseline image or images, generating a foreground.Pixels in the foreground change. Yet pixels used in imaging a person'storso will likely change more slowly than a person's hand as theperson's hand reaches for an item. Thus, the pixels in the foregroundthat have a greater amount of change than other pixels in the foregroundare used to determine if a hand is present. Artificial intelligence isused to identify if a hand is present in a frame.

In step 620, a processor resolves if the hand is holding an object. Insome embodiments, artificial intelligence is used to determine if thehand is holding an object. In some embodiments, the artificialintelligence doesn't determine what the object is, but simply determinesthat the hand is holding an object. In some embodiments, the artificialintelligence determines what the object is.

In step 628 state vectors are recorded corresponding to the plurality offrames. The state vectors are based on resolving if the hand holds anobject. In some embodiments, two hands are tracked. In some embodiments,a state vector includes one or more of: hand1_presence, hand1_location,hand1_product_present, hand1_productidentifier, hand2_presence, hand2location, hand2_product_present, and hand2_productidentifier.

In step 632, the object is detected as being removed or added to thedisplay based on the state vectors and a time sequence of the pluralityof frames.

In some embodiments, in the store, overhead-mounted cameras stream videoas soon as the shopping session begins (e.g., the shopper enters thestore and/or opens the door). In this example, video images aretransmitted wirelessly to another location where they are analyzed on aserver. The system uses efficient compression of the video sequence inorder to not overload the wireless channel. In some embodiments, thecomplete video sequences of the shopping event are transmitted andstored for potential later review in a case where suspicious behavior isdetected.

The image processing system uses one or more of the following:

1. Activities relating to picking of product involve the shopper'shands.

2. Moving objects and/or body parts are of interest. In someembodiments, moving objects and/or body parts are the only aspects ofimages that are of interest.

3. In embodiments that allow only one person in the store and/or space,a maximum number of hands to be tracked is two.

4. Since only one person is allowed in the store, in some embodimentsthe system does not associate hands with a particular shopper. Rather,the association is already complete by identifying the shopper at thedoor.

In some embodiments, an algorithm breaks down in a number of steps:

1. Pick one image frame from the video sequence.

2. Determine if the image frame is usable by checking if the image isclear enough for the algorithm to be successful. This is accomplished bychecking on the high frequency content on the image frame and comparingit to other similar images.

3. Detect the “moving” objects in the image frame by comparingindividual pixels to previous image frames of the same scene.

4. Detect if there are one or more hands among the moving objects in theframe.

5. For each detected hand, determine if the hand holds an object(product) and/or how many.

6. For each detected hand, determine the location of the hand relativeto the retail display shelf.

7. For each detected product, optionally identify the product, ifpossible.

8. Record the state vector P_i={hand1_presence, hand1_location,hand1_product_present, hand1_productidentifier, hand2_presence,hand2_location, hand2_product_present, hand2_productidentifier}

9. Go back to step #1 and repeat for the next frame.

In some embodiments, steps 2, 3, 4 and 5 are implemented using neuralnetwork models that are trained on previously recorded video sequencesof similar shopping scenes. Training sequences are being obtained usingone or more methods:

1. Video record acted shopping behavior and label the sequencesaccording to labels A, B, C, D below.

2. Video record actual shoppers in real-life stores and label thebehavior according to A, B, C, D below.

3. Video record actual shoppers in real-life stores and infer theoverall count and product list from the shopper's bill of sale/receipt.

4. Use footage in the store. As the shopper is scanning items on hermobile phone, a labeled sequence of images of a particular event andproduct is created.

5. Use video footage from existing security cameras in a variety ofstores and label sequences according to labels A, B, C, D below.

6. Take images of product at the checkout line in a regular store. Atthe time of checkout, images of a particular product are created whileat the same time the product is identified typically using barcodetechnology.

In a second part of the processing algorithm, the system analyzes asequence of state vectors SP in the form of SP={P_i, P_i+1, P_i+2, . . ., P_i+N}, using the following steps:

1. Find the first P with a product present (P=P_k) in hand1 and/or hand2(in the following we use the example of hand1).

2. Set SP_k={P_k−L, . . . , P_k, . . . , P_k+M}, where L and M are largeenough so that the entire handing of the product is captured.

3. Establish the trajectory of the product by looking at thehand1_product_present field and the hand1_location fields. This resultsin a number of possible situations considering times k−L and k+M.Depending on which situation applies. N_k is assigned the value in thelast column.

Time_k-L + Time k + Time k-L q M Event N_k Empty hand Hand holding Handwith A: Product =+1 * number removed from product near product awayremoved of prod- shelf shelf from shelf from shelf ucts_present Handwith Hand holding Empty hand B: Product =−1 * number product awayproduct near removed replaced of prod- from shelf shelf from shelf onshelf ucts_present Hand with Hand holding Hand with C: Product =0product away product near product remains from shelf shelf removed withfrom shelf shopper Hand without Hand holding Hand without D: Product =0product away product near product remains from shelf shelf removed onshelf from shelf4. Find the next P where a product is present and repeat step 1 to 3.The total count of products picked is computed as N_total=N_1+N2+N3+ . .. +N_K.

Referring next to FIG. 7, an exemplary environment with whichembodiments may be implemented is shown with a computer system 700 thatcan be used by a designer 704 to design, for example, electronicdesigns. The computer system 700 can include a computer 702, keyboard722, a network router 712, a printer 708, and a monitor 706. The monitor706, processor 702 and keyboard 722 are part of a computer system 726,which can be a laptop computer, desktop computer, handheld computer,mainframe computer, etc. The monitor 706 can be a CRT, flat screen, etc.

A designer 704 can input commands into the computer 702 using variousinput devices, such as a mouse, keyboard 722, track ball, touch screen,etc. If the computer system 700 comprises a mainframe, a designer 704can access the computer 702 using, for example, a terminal or terminalinterface. Additionally, the computer system 726 may be connected to aprinter 708 and a server 710 using a network router 712, which mayconnect to the Internet 718 or a WAN.

The server 710 may, for example, be used to store additional softwareprograms and data. In one embodiment, software implementing the systemsand methods described herein can be stored on a storage medium in theserver 710. Thus, the software can be run from the storage medium in theserver 710. In another embodiment, software implementing the systems andmethods described herein can be stored on a storage medium in thecomputer 702. Thus, the software can be run from the storage medium inthe computer system 726. Therefore, in this embodiment, the software canbe used whether or not computer 702 is connected to network router 712.Printer 708 may be connected directly to computer 702, in which case,the computer system 726 can print whether or not it is connected tonetwork router 712.

With reference to FIG. 8, an embodiment of a special-purpose computersystem 800 is shown. The above methods may be implemented bycomputer-program products that direct a computer system to perform theactions of the above-described methods and components. Each suchcomputer-program product may comprise sets of instructions (codes)embodied on a computer-readable medium that directs the processor of acomputer system to perform corresponding actions. The instructions maybe configured to run in sequential order, or in parallel (such as underdifferent processing threads), or in a combination thereof. Afterloading the computer-program products on a general-purpose computersystem 726, it is transformed into the special-purpose computer system800.

Special-purpose computer system 800 comprises a computer 702, a monitor706 coupled to computer 702, one or more additional user output devices830 (optional) coupled to computer 702, one or more user input devices840 (e.g., keyboard, mouse, track ball, touch screen) coupled tocomputer 702, an optional communications interface 850 coupled tocomputer 702, a computer-program product 805 stored in a tangiblecomputer-readable memory in computer 702. Computer-program product 805directs system 800 to perform the above-described methods. Computer 702may include one or more processors 860 that communicate with a number ofperipheral devices via a bus subsystem 890. These peripheral devices mayinclude user output device(s) 830, user input device(s) 840,communications interface 850, and a storage subsystem, such as randomaccess memory (RAM) 870 and non-volatile storage drive 880 (e.g., diskdrive, optical drive, solid state drive), which are forms of tangiblecomputer-readable memory.

Computer-program product 805 may be stored in non-volatile storage drive880 or another computer-readable medium accessible to computer 702 andloaded into memory 870. Each processor 860 may comprise amicroprocessor, such as a microprocessor from Intel® or Advanced MicroDevices, Inc.®, or the like. To support computer-program product 805,the computer 702 runs an operating system that handles thecommunications of product 805 with the above-noted components, as wellas the communications between the above-noted components in support ofthe computer-program product 805. Exemplary operating systems includeWindows® or the like from Microsoft Corporation, Solaris® from SunMicrosystems, LINUX, UNIX, and the like.

User input devices 840 include all possible types of devices andmechanisms to input information to computer system 702. These mayinclude a keyboard, a keypad, a mouse, a scanner, a digital drawing pad,a touch screen incorporated into the display, audio input devices suchas voice recognition systems, microphones, and other types of inputdevices. In various embodiments, user input devices 840 are typicallyembodied as a computer mouse, a trackball, a track pad, a joystick,wireless remote, a drawing tablet, a voice command system. User inputdevices 840 typically allow a user to select objects, icons, text andthe like that appear on the monitor 706 via a command such as a click ofa button or the like. User output devices 830 include all possible typesof devices and mechanisms to output information from computer 702. Thesemay include a display (e.g., monitor 706), printers, non-visual displayssuch as audio output devices, etc.

Communications interface 850 provides an interface to othercommunication networks and devices and may serve as an interface toreceive data from and transmit data to other systems, WANs and/or theInternet 718. Embodiments of communications interface 850 typicallyinclude an Ethernet card, a modem (telephone, satellite, cable, ISDN), a(asynchronous) digital subscriber line (DSL) unit, a FireWire®interface, a USB® interface, a wireless network adapter, and the like.For example, communications interface 850 may be coupled to a computernetwork, to a FireWire® bus, or the like. In other embodiments,communications interface 850 may be physically integrated on themotherboard of computer 702, and/or may be a software program, or thelike.

RAM 870 and non-volatile storage drive 880 are examples of tangiblecomputer-readable media configured to store data such ascomputer-program product embodiments, including executable computercode, human-readable code, or the like. Other types of tangiblecomputer-readable media include floppy disks, removable hard disks,optical storage media such as CD-ROMs, DVDs, bar codes, semiconductormemories such as flash memories, read-only-memories (ROMs),battery-backed volatile memories, networked storage devices, and thelike. RAM 870 and non-volatile storage drive 880 may be configured tostore the basic programming and data constructs that provide thefunctionality of various embodiments, as described above.

Software instruction sets that provide the functionality of someembodiments may be stored in RAM 870 and non-volatile storage drive 880.These instruction sets or code may be executed by the processor(s) 860.RAM 870 and non-volatile storage drive 880 may also provide a repositoryto store data and data structures used in accordance with someembodiments. RAM 870 and non-volatile storage drive 880 may include anumber of memories including a main random access memory (RAM) to storeof instructions and data during program execution and a read-only memory(ROM) in which fixed instructions are stored. RAM 870 and non-volatilestorage drive 880 may include a file storage subsystem providingpersistent (non-volatile) storage of program and/or data files. RAM 870and non-volatile storage drive 880 may also include removable storagesystems, such as removable flash memory.

Bus subsystem 890 provides a mechanism to allow the various componentsand subsystems of computer 702 communicate with each other as intended.Although bus subsystem 890 is shown schematically as a single bus,alternative embodiments of the bus subsystem may utilize multiple bussesor communication paths within the computer 702.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments may be practiced without these specific details.For example, circuits may be shown in block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquesmay be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove may be done in various ways. For example, these techniques,blocks, steps and means may be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitsmay be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations may be re-arranged. A process is terminated when itsoperations are completed, but could have additional steps not includedin the figure. A process may correspond to a method, a function, aprocedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination corresponds to a return of the functionto the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks may bestored in a machine-readable medium such as a storage medium. A codesegment or machine-executable instruction may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment may becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. may be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, token passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory. Memory may be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may representone or more memories for storing data, including read only memory (ROM),random access memory (RAM), magnetic RAM, core memory, magnetic diskstorage mediums, optical storage mediums, flash memory devices and/orother machine readable mediums for storing information. The term“machine-readable medium” includes, but is not limited to portable orfixed storage devices, optical storage devices, wireless channels,and/or various other storage mediums capable of storing that include orcarry instruction(s) and/or data.

A number of variations and modifications of the disclosed embodiment(s)can also be used. For example, the mobile device 104 can be used in lieuof or in addition to the scanner 132. In some embodiments, the areaenclosed by the structure allows a person's entire body to enter thearea (e.g., FIG. 3); in some embodiments, the area enclosed by thestructure does not allow a person's entire body to enter the area (e.g.,FIG. 5). The result in the description of FIG. 2 can be transmitted forcredit reporting. If the result in the description of FIG. 2 is non-zeroand the item missing from the scanned items is under a threshold value(e.g., less than $5, $2, $1, or $0.50), then a note is made to therecord and the user is able to check out without delay. But if the userhas multiple instances of a non-zero report, then the user is prohibitedfrom using the service. In some embodiments, a credit card and/or othertype of payment is linked to an account of the user and is charged aftera transaction. In some embodiments, the cameras 120 don't track a userin the area (e.g., to conserve bandwidth and processing speed). In someembodiments, the cameras 120 do track the user in the area. In someembodiments, the registry is purged after a user completes a shoppingexperience to save memory and/or enable the processing unit 106 to runmore efficiently. In some embodiments, video data in local storage istransferred to a remote storage, and the video data in the local storageis purged (e.g., weekly, daily, every 12 hours, and/or after a shoppingtransaction is completed by a user) so that the local storage and/or theprocessing unit 106 can run more efficiently. Though this descriptionprovides examples using a door for access control, other access controlscould be used. For example, physical access can be provided by one ormore of the following: cabinet door, turnstile, store door, slidingdoor, swing door, fridge door, lock, bike lock, and/or optical gate.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

FIG. 9 depicts exemplary merchant database 902 and user database 904.Merchant database 902 (e.g. one or more parts of store database 136and/or one or more parts of product database 144) and user database 904(e.g. one or more parts of consumer database 140) may store information(e.g. data points) associated with a user session. A user session may beestablished once a user enters into a specific area (e.g., store 102).In one embodiment, a user may be authenticated prior to initiating auser session. For example, a user may be authenticated prior to beingallowed entry into an area. Data may be gathered during a user sessionsuch as data from one or more sensors (e.g., one or more cameras 120)that is associated with one or more items (e.g., item 116) within thearea. As shown in FIG. 9, data within merchant database 902 may includea user session identifier (ID), a user ID, encrypted automaticidentification and data capture (AIDC) information, encrypted sensordata, entry time associated with a user session, exit time associatedwith the user session, a session location, one or more results, and aledger pointer.

A user session ID may include an identifier associated with a usersession. The user session identifier may be a numeric value,alphanumeric value, or any other value that may uniquely identify a usersession within a database. Each separate time a user enters an area anew user session ID may be generated. A user ID may include anidentifier associated with the user. The user ID may be a numeric value,alphanumeric value, or any other value that may uniquely identify a userwithin a database.

Encrypted AIDC information may include any information that identifiesan item within the area that is encrypted by a key. Information thatidentifies an item may be stored in a machine readable format such asbar code, RFID, magnetic strip, quick response (QR) code, and the like.The machine readable format may be affixed to an item itself. Forexample, the machine readable format may be presented as a label affixedto an item. Information that identifies an item may be a serial numberassociated with an item. The key used to encrypt the AIDC may be amerchant key. The merchant key may be an encryption key associated witha merchant. A merchant may be a provider of one or more items within thearea. In one embodiment, a merchant may be a provider of the areaitself. The merchant key be a symmetric key or a public key associatedwith the merchant. In circumstances when the merchant key is a publickey the encrypted AIDC information may be encrypted with the merchantpublic key and the merchant may hold or control access to (e.g., via apassword, biometric information of the merchant, and the like) theprivate key associated with the merchant public key.

Encrypted sensor data may include sensor data that identifies one ormore actions taken during a user session. User action may be a userremoving a specific item from the area, removing a specific item from ashelf in the area, displacing a specific item from a first location to asecond location, entering the area, leaving the area, and the like.Sensor data may be captured by various sensors or other devices. Forexample, sensor data may be captured by one or more cameras within thearea. In one embodiment, sensor data may include personally identifiableinformation of a user. Personally identifiable information may include,but not be limited to, the face of the user, a visually distinguishingcharacteristic of the user, biometric information of the user, apassport number associated with the user, a driver's license numberassociated with the user, handwriting associated with the user, ageographic location associated with the user, a race or nationalityassociated with the user, or any other information that may be utilizedto personally identify a user. In one embodiment, within merchantdatabase 902, AIDC and sensor data are both encrypted with the merchantkey.

In one embodiment, encrypted sensor data within merchant database 902may not include personally identifiable information associated with auser. Instead, the personally identifiable information may be stored asencrypted sensor data within user database 904. In such an instance, theencrypted sensor data within merchant database 902 may include sensordata with redacted personally identifiable information (e.g., video of auser within the area with his face blurred). The encrypted sensor datawithin user database 904 may be encrypted by a user key associated witha user. The user key may be a symmetric key or a public key associatedwith the user. In circumstances when the user key is a public key theencrypted sensor data within user database 904 may be encrypted with theuser public key and the user may hold or control access to (e.g., via apassword, biometric information of the user, and the like) the privatekey associated with the user public key. By providing two differenttypes of encrypted sensor data a user may control access theirpersonally identifiable information in compliance with various laws andregulations such as General Data Protection Regulation (GDPR).

An entry time may include a timestamp associated with a time when a userenters the area. Similarly, an exit time may include a timestampassociated with a time when a user exits the area. Together the entrytime and exit time may indicate a user session duration.

A session location may include a unique indication of the location ofthe area. In one embodiment, a user may have access to a plurality ofdifferent areas. In such an instance, the session location indicates theparticular area associated with a user session.

A result may include transaction information associated with a usersession. A result may include the identification of one or more itemsremoved from the area during a user session. For example, a result mayindicate a number of items indicated as being removed from the areaaccording to sensor data, a number of items indicated as being removedfrom the area according to AIDC information, a discrepancy between thenumber of items indicated as being removed from the area according toAIDC information and the number of items indicated as being removed fromthe area according to sensor data. A result may further indicatespecific items that were displaced, removed, or relocated during a usersession (e.g., moved from a first shelf to a second shelf or moved froma first self to a bag). In one embodiment, a result may be laterverified or validated based on one or more data points within merchantdatabase 902, user database 904, and/or a decentralized database.

A ledger pointer may include a pointer or link to a block or segmentwithin a distributed ledger (e.g., decentralized database) associatedwith a user session. The distributed ledger may contain uniqueidentifiers associated with one or more aspects of a user session. Inone embodiment, a unique identifier may be generated using dataassociated with a user session (e.g., encrypted sensor data frommerchant database 902 or encrypted sensor data from user database 904)as an input into a cryptographic function (e.g., a hash function).Because this unique identifier is stored in a separate location theledger pointer identifies and/or links to the storage location of theunique identifier.

Some data associated with a user session may be different betweenmerchant database 902 and user database 904. In one embodiment, whenevera user session is initiated user session information is stored withintwo distinct centralized databases (i.e. merchant database 902 and userdatabase 904). Some of the information in both databases may be thesame. For example, as indicated in FIG. 9, the user session with theuser session ID of abc123 has similar values for user session ID, userID, entry time, exit time, session location, result, and ledger blockpointer within merchant database 902 and user database 904. These datapoints may be synchronized between the merchant database 902 and userdatabase 904 so that these values are the same. However, some of theinformation such as the encrypted sensor data may be different betweenmerchant database 902 and user database 904 for a user session. Forexample, as indicated in FIG. 9, the user session with the user sessionID of abc123 has different values for encrypted sensor data withinmerchant database 902 and user database 904. In one embodiment, theencrypted sensor data values may be different because two different keys(e.g., a user key and a merchant key) were utilized to encrypt thesensor data. In one embodiment, the encrypted sensor data values may bedifferent because the encrypted sensor data within merchant database 902is stripped of personally identifiable information, whereas theencrypted sensor data within user database 904 contains the personallyidentifiable information. In one embodiment, as depicted in FIG. 9, userdatabase 904 may omit encrypted AIDC information (or AIDC information)as this information may be more relevant to a merchant than a user.Although merchant database 902 is shown with only two encrypted parts(e.g., encrypted AIDC information and encrypted sensor data) one or moreother data points associated with a user session may be encrypted by amerchant key and stored within merchant database 902. For example, theresult within merchant database 902 may be encrypted by the merchantkey. Similarly, although user database 904 is shown with only oneencrypted part (e.g., encrypted sensor data) one or more other datapoints associated with a user session may be encrypted by a user key andstored within user database 904. For example, the ledger pointer withinuser database 904 may be encrypted by the user public key. By utilizingtwo distinct data stores (e.g., merchant database 902 and user database904) there may be two records of a user session within the area suchthat if one is corrupted the other may be relied upon (i.e., dataredundancy). In addition, by utilizing two distinct data stores a usermay control access to one or more aspects of his data associated with auser session. For example, encrypted sensor data with personallyidentifiable information may only be stored within user database 904 andencrypted with a user key. Thus, preventing anyone besides the user fromaccessing personally identifiable information associated with a usersession. In one embodiment, each row of user database 904 is stored notwithin a single database but instead on a user's device such that auser's own session information may be locally stored on a device localto a user (e.g., a mobile phone, tablet, personal computer).

In one embodiment, merchant database 902 and/or user database 904 maycontain voluminous and large amounts of data (e.g., encrypted AIDC andencrypted sensor data) associated with a plurality of user sessions.Such data may not be practically stored within a distributed ledger.However, the ledger pointer may point to a particular block or segmentwithin a distributed ledger that may contain information that may beutilized to verify or validate a result indicated in merchant database902 and user database 904. For example, the distributed ledger maycontain a cryptographically immutable unique identifier that representsan aspect (e.g., encrypted AIDC data, encrypted sensor data, and thelike) of a user session. The unique identifier may be then used toverify a result by indicating if one or more aspects of the user sessionhas been maliciously altered by any party. Because, in part, usersession data is stored in two separate records either party maymaliciously attempt to alter records that they may have access to inorder to invalidate or alter a result. By utilizing a distributed ledgerin addition to merchant database 902 and user database 904 maliciousactions by parties may be detected and results may be validated orverified.

For example, suppose the result in merchant database 902 and userdatabase 904 indicate that a user removed a specific item from aspecific area during a user session. Data points associated with thatsession may be duplicated and stored within merchant database 902 anduser database 904 (although some data points may be different asdescribed above). In one embodiment, a merchant may attempt to maliciousmodify the result associated with the user session. Thus, the result inuser database 904 and result in merchant database 902 may be different.To combat this issue, a hash of the result (when generated) may begenerated to form a unique identifier. Any suitable hash algorithm maybe utilized such as SHA-256. The unique identifier may be then writtento a block or segment with a distributed ledger. This block may bereferenced by a ledger pointer associated with the user session. Whenthe merchant attempts to indicate to the user the malicious result, boththe user and the merchant may, via the ledger pointer, acquire theunique identifier that indicates a hash of the result. Because themerchant has maliciously altered the result when the merchant hashes theresult from merchant database 902 it will not match the uniqueidentifier that is indicated by the ledger pointer. However, the resultin user database 904 when hashed may match the unique identifier that isindicated by the ledger pointer because the result in the user database904 has not been maliciously altered. As a result, utilizing adistributed ledger, voluminous data points stored within differentdatabases may be verified or validated without having to storevoluminous data points within the distributed ledger itself.

FIG. 10 illustrates decentralized database 1002 which is an exemplarydecentralized database (i.e. distributed ledger) in accordance with oneor more embodiments. Decentralized database 1002 may be stored in aplurality of computing devices. Each computing device may contain a copyof decentralized database 1002. Decentralized database 1002 may be ablockchain comprising a plurality of cryptographically linked blocks1004, 1008, 1012, and 1016. Blocks 1004, 1008, 1012, and 1016 may becryptographically linked by hash functions 1006, 1010, and 1014. Each ofblocks 1004, 1008, 1012, and 1016 may contain one or more uniqueidentifiers and each block may be considered a segment of decentralizeddatabase 1002. For example, block 1004 comprises unique identifier 1,unique identifier 2, unique identifier 3, and unique identifier 4. Eachunique identifier may be a cryptographic representation of one or moredata points associated with a user session in a specific area. Forexample, a unique identifier within blocks 1004, 1008, 1012, and 1016may be generated utilizing a hash function (e.g., SHA-256) and one ormore data points within merchant database 902 and/or user database 904as depicted in FIG. 9. In such an example, a unique identifier may begenerated based on encrypted sensor data. Furthermore, a uniqueidentifier may be generated to provide an immutable description of anitem within an area. For example, a unique identifier may acryptographically generated unique identifier based on an image of oneor more items, AIDC data, numerical item identifiers, locationinformation associated with an item or a user session. In such anexample, a unique identifier may established evidence that an item or auser was in a certain a certain state at a certain time. In such anexample, an image or identifier of an item and a timestamp may be usedas input into a cryptographic function generate a unique identifier toindicate a state of an item at a given time. If later the item is brokenor missing then the unique identifier may be a cryptographicallyimmutable reference that the item was not previously broken or missingat an early time.

Block 1004 may be a genesis block within decentralized database 1002. Agenesis is the first block within a blockchain. Block 1004 may contain aplurality of unique identifiers from a single user session or frommultiple user sessions. In one embodiment, each block withindecentralized database 1002 may contain only unique identifiersassociated with a single user session. In such an embodiment, block 1004may contain unique identifiers for encrypted sensor data, sessionlocation information, user ID, entry and exit times, and the like for asingle user session. In one embodiment, each block within decentralizeddatabase 1002 may contain unique identifiers associated with multipleuser sessions.

Block 1004 may be an input into hash 1006 and the resulting hash (i.e.block 1004 hash) may be implemented (e.g., within the header or withinthe body) into block 1008. Block 1008 may comprise unique identifiers5-10 in addition to the hash of block 1004. Block 1008 may then be inputinto hash 1010 and the resulting hash (i.e. block 1008 hash) may beimplemented into block 1012. This cryptographically linking process maycontinue for blocks 1012 and 1016. By including a hash of the previousblock into a current block, the previous block may becomecryptographically immutable. For example, the hash of block 1004 may berepresented in block 1016 because block 1016 includes a hash of block1012, which includes a hash of block 1008, which includes a hash ofblock 1004. As a result, if any information in block 1004 is modified,that would in turn modify every subsequent block (e.g., block 1008,block 1012, and block 1016). Such a change would modify the blockchainwithin a noticeable way. Thus, making any changes in previous blockseasily detectable and ensuring previous blocks contain unmodified datapoints. As can be seen from the previous description, multiple databases(e.g., user database 904 and merchant database 902) may be utilized tostore a plurality of files that may be large (e.g., 5 MB, 10 MB, 100 MB,1 GB, and the like) while decentralized database 1002 may be utilized toverify one or more data points stored within the multiple databases.

In one embodiment, a different distributed database associated withdigital assets (e.g., cryptocurrencies) may be utilized in conjunctionwith decentralized database 1002. For example, the different distributeddatabase may be a distributed ledger that stores indications oftransactions associated with a digital asset. This digital asset may beutilized in various aspects of embodiments. For example, a digital assetmay be utilized for one or more of the following: as payment for one ormore items within an area, and as payment to a reviewer (or an oraclereviewing) of a result (e.g. result stored within a merchant database oruser database). In instances where the digital asset is used for paymentof one or more items, upon initializing a user session, a user's digitalwallet (which identifies a quantity of the digital asset) may beaccessed and a temporary hold may be placed on a predetermined quantityof a user's digital assets to act as collateral. Such collateral mayensure that a user pays for one or more removed (e.g., purchased) items.In instances where the digital asset is used as payment to a reviewer ororacle, a reviewer or an oracle may be provided that may verify a resultwithin a merchant database and/or user database based on informationwithin information within the merchant database, the user database,and/or a decentralized database. An oracle or reviewer may perform theprocess as shown in FIG. 14 block 1435. For example, an oracle mayreview decrypted sensor data to determine how many items a user removedduring a user session and may be compensated for the review.

In addition to digital assets, the different distributed database mayalso support smart contracts. A smart contract may be code stored withinthe different distributed database that is cryptographically immutableand automatically executes if certain coded conditions are met. A smartcontract may be utilized within various embodiments. For example, when auser uses a digital asset as payment, a smart contract may receive, asan input, the payment from the user for an item and may output, after acertain period of time (e.g., 30 days), the payment back to the user(e.g., when the item is returned) or to a merchant associated with theitem (e.g., when the item is not returned). Such an embodiment may allowdispute resolution where there is no central trusted third party toprocess a payment (e.g., bank). In another example, when there is atemporary hold placed on a predetermined quantity of a user's digitalassets as collateral, a smart contract may facilitate the temporaryhold. In such an example, the smart contract may receive, as inputs, oneor more of: an identity of the user (e.g., user ID), purchase history ofthe user, rating of a user, type of items offered in a specific areaassociated with a user, the average transaction amount associated with aspecific area, the amount of inventory at a specific location and thelike, and output, based on code comprising the smart contract, thequantity of a user's digital assets that should be taken as collateral.

FIG. 11 illustrates process 1100 that may be an exemplary process forinitiating a user session and recording data associated with a usersession. Process 1100 may be implemented by one or more systems (e.g.,processing unit 106 as referend by FIG. 1). At 1105, a system receivesan access request associated with a user. A user, if authenticated, maygain access to a specific area (e.g., enclosure 108 as referenced byFIG. 1). The area may be an enclosed area. The access request mayinclude some type of user authentication information such as userbiometric information, a password, a user identifier, a telephonenumber, and/or a combination of any of the previously listed elements.

At 1110, the system authenticates the user associated with the accessrequest and initiates a user session. The system may authenticate theuser by comparing the authentication information received at 1105 withpreviously stored authentication information. For example, the systemmay determine a password in the received access request matches apreviously stored password. After the user is authenticated, a specificarea may be physically unlocked or made available to the user. Forexample, the system may send a signal to a locking mechanism at the areato unlock the locking mechanism in order to allow the user to enter thearea. In one embodiment, the area may have a motion sensor that a usermay activate by walking across. Once a signal from the motion sensor isreceived by the system a user session may be initiated. To initiate auser session, the system may allocate storage within one or moredatabases (e.g., a user database and/or merchant database) for datapoints associated with the user session. In one embodiment, theallocated storage may be identified by a unique user session identifier.

At 1115, the system receives sensor data associated with the usersession. Sensor data may include data that identifies one or more useractions taken during a user session. In one embodiment, sensor data mayinclude personally identifiable information of a user. In oneembodiment, sensors that acquire sensor data may be affixed to thespecific area associated with a user session. The system may, uponreceiving sensor data, identify personally identifiable informationwithin the sensor data. Personally identifiable information may beidentified based on various techniques such as facial recognition,optical character recognition (to determine if displayed documentscontain sensitive information such as passport numbers, credit cardnumbers etc.), iris scans, finger print readers, hand scanners, and thelike. The received sensor data may then be stored to an allocatedportion of one or more databases. In one example, the sensor data may bereceived by the system and the system may determine personallyidentifiable information within the sensor data. The system may thenproduce two versions of the sensor data, a merchant version containingno personally identifiable information, and a user version containingthe personally identifiable information. The system may then encrypt andstore the merchant version of the sensor data within a merchant databaseand encrypt and store the user version of the sensor data within a userdatabase. Prior to or after storing the received sensor data, the systemmay identify a result based on the received sensor data and store theresult within one or more databases. Stored sensor data and resultsassociated with stored sensor data may be associated with or linked withthe user session identifier associated with the user session initiatedat 1110. The one or more databases may be stored in the same physicallocation or in different physical locations. The one or more databasesmay be implemented on the same computing platform or in a differentcomputing platform. For example, a first database may be implemented asSQL database and a second database may be implemented as a DB2 database.

At 1120, the system receives AIDC data (information) associated with theuser session. In one embodiment, AIDC data may include any informationthat identifies an item within the specific area associated with a usersession. In one embodiment, the system receives AIDC data from one ormore scanners within the area. In one embodiment, the devices whichrecord and transmit AIDC data to the system are different from thedevices that record and transmit sensor data to the system. The systemmay encrypt and store received AIDC database in a plurality of databases(e.g., merchant database and/or user database). Prior to or afterstoring received AIDC data, the system may identify a result based onthe received AIDC data and store the result within one or moredatabases. Stored AIDC data and results associated with stored AIDC datamay be associated with or linked with the user session identifierassociated with the user session initiated at 1110.

FIG. 12 illustrates process 1200 that may be a first exemplary processfor establishing access rights to information associated with a usersession. Process 1200 may be implemented by one or more systems (e.g.,processing unit 106 as referend by FIG. 1). In one embodiment, process1200 may be implemented after a user session has been initiated (e.g.block 110 of FIG. 11). At 1205, a system encrypts, with a first key, afirst instance of user session data and store the encrypted firstinstance in a first database. User session data may be generated by oneor more devices affixed to a specific area associated with a usersession. User session data may include, but not be limited to, a usersession ID, a user ID, AIDC data (information), sensor data, entry time,exit time, user session location, a result associated with the usersession, and/or a ledger pointer associated with the user session. Thesystem may receive user session data throughout an active user sessionwithin the area. The system may then store within a first database(e.g., a merchant database) received (or calculated (e.g., a result))user session information that has been encrypted by a first key (e.g.,merchant key). In one embodiment, only a portion of the received (orcalculated) user session information is encrypted by the first key,which means one or more portions of user session information (e.g.,entry time and exit time) may be stored in an unencrypted form withinwith the first database.

At 1210, the system encrypts, with a second key, a second instance ofthe user session data and stores the encrypted second instance in asecond database. The system may duplicate the received user session dataand encrypt the duplicated data with a second key and store theencrypted data in a second database. The second database may be adatabase associated with a user (e.g., a user database) and the secondkey may be a key associated with the user (e.g., user key). In oneembodiment, only a portion of the received (or calculated) user sessioninformation is encrypted by the second key, which means one or moreportions of user session information may be stored in an unencryptedform within the second database. In one embodiment, the second databasemay include encrypted information not stored in the first database. Forexample, when user session data includes personally identifiableinformation. This personally identifiable information may be removed foruser session data encrypted and stored in the first database, but may beincluded in the user session data encrypted and stored in the seconddatabase. By creating multiple instances of user session data there maybe two separate databases that store user session data, which mayprovide data redundancy. Furthermore, each database may have differentaccess controls associated with them which may increase informationsecurity.

At 1215, the system generates a unique identifier associated with theuser session data and stores within a third database the uniqueidentifier. One or more aspects of received user session data may beutilized to generate a unique identifier. In one embodiment, a uniqueidentifier may be generated using data associated with a user session(e.g., encrypted sensor data) as an input into a cryptographic function(e.g., a hash function). The unique identifier may be generated at thesame time or near the same time that the user session data is received.By generating the unique identifier at a time close to when the usersession data is received it may assure that the unique identifier is anaccurate representation of one or more data points associated with usersession data. For example, whenever the system receives sensor data froma user session the system may simultaneously or near simultaneouslyencrypt and store the sensor data within the first database, encrypt andstore the sensor data within the second database, and generate and storewithin the third database the unique identifier for the sensor data. Thefirst, second, and third databases may be distinct data stores. In oneembodiment, the first and second databases may be implemented ascentralized databases and the third database may be a decentralizeddatabase. In such embodiment, data within the third database may beutilized to verify data within the first and second databases.

FIG. 13 illustrates process 1300 that may be a second exemplary processfor establishing access rights to information associated with a usersession. Process 1300 may be implemented by one or more systems (e.g.,processing unit 106 as referend by FIG. 1). In one embodiment, process1300 may be implemented after a user session has been initiated (e.g.block 110 of FIG. 11). At 1305, the system identifies personallyidentifiable information from received sensor data associated with auser session. The system may, upon receiving sensor data, identifypersonally identifiable information within the sensor data. Personallyidentifiable information may be identified based on various techniquessuch as facial recognition, optical character recognition (to determineif displayed documents contain sensitive information such as passportnumbers, credit card numbers etc.) and the like.

At 1310, the system may segment the personally identifiable informationfrom the sensor data to generate a first dataset and a second dataset.The first dataset may include sensor data that is absent of personallyidentifiable information. The first dataset may include sensor data withpersonally identifiable information removed, blurred, obfuscated, andthe like. For example, sensor data, within the first dataset, mayinclude one or more video frames of a user within a specific areaassociated with a user session with the user's face blurred out. Thesecond dataset may include sensor data that includes personallyidentifiable information. For example, sensor data, within the seconddataset, may include one or more video frames of a user within aspecific area associated with a user session that shows the user's face.

At 1315, the system encrypts, with a first key, the first dataset andstores within a first database the encrypted first dataset. The firstkey may be associated with a merchant. The merchant may provide one ormore items within a specific area associated with a user session. Themerchant may control access to the merchant key. The first database maybe a database associated with the merchant.

At 1320, the system encrypts, with a second key, the second dataset andstores within a second database the encrypted first dataset. The secondkey may be associated with a user. The user may interact with one ormore items within a specific area associated with a user session. Theuser may control access to the user key. The second database may be adatabase associated with the user.

At 1325, the system generates a unique identifier based on the encryptedsecond dataset and stores within a third database the unique identifier.In one embodiment, the unique identifier may be generated using theencrypted second dataset as an input into a cryptographic function(e.g., a hash function). The unique identifier may be included within ablock or segment within the third database. In one embodiment, the thirddatabase is implemented by a blockchain. By inputting the uniqueidentifier into a block of a blockchain the unique identifier may becryptographically immutable and can be later used to verify a user (oranother malicious actor) has not modified the encrypted second dataset.Such verification may be important because a merchant may not haveaccess to the second dataset because the second dataset is encrypted bya user key. Thus, a merchant may not know if a user (or anothermalicious actor) modifies stored sensor data with personallyidentifiable information.

FIG. 14 illustrates process 1400 that may be an exemplary process forverifying a result associated with a user session. Process 1400 may beimplemented by one or more systems (e.g., processing unit 106 asreferend by FIG. 1). Process 1400 may be a continuation of process 1300(as depicted in FIG. 13) and may occur after process 1300 has ended. At1405, the system receives, a verification request for a resultassociated with a user session. A result may include transactioninformation associated with a user session. A result may include theidentification of one or more items removed from a particular areaduring a user session. The system may determine a result based onvarious data points associated with a user session (e.g., sensor data,AIDC information, and the like). A user or another party (e.g., amerchant) associated with a result may send to the system theverification request. The verification request may include a usersession identifier to identify the session in question as well as theresult identifier to identify the result in question.

At 1410, the system receives the encrypted second dataset. As detailedat 1310 of FIG. 13, the second dataset includes sensor data withpersonally identifiable information. The second dataset is furtherencrypted by a second key associated with a user. The system may, uponreceiving the verification request, request the encrypted second datasetfrom the user or may retrieve the encrypted second dataset from a userdatabase. Because the second dataset is encrypted with a second key andthe user controls access to the second key, the system may not be ableto decrypt the encrypted second key without permission from the user.However, the system may still be able to determine if any modificationswere performed to the encrypted second dataset.

At 1415, the system hashes the encrypted second dataset to generate afirst hash value. At 1420, the system compares the first hash value to aunique identifier associated with the user session. User session datamay indicate a ledger pointer associated with a user session. The ledgerpointer may point to a block within a decentralized database thatcontains a unique identifier. The unique identifier may have beengenerated by hashing a previously generated version of the encryptedsecond dataset. The ledger pointer may also identify the hashingalgorithm utilized to create the unique identifier. The system may usethis same hashing algorithm to generate the first hash value at 1415. Bygenerating the first hash value and comparing the first hash value to aunique identifier it can be determined if the received encrypted seconddataset (at 1410) has been altered. If the first hash value does notequal the unique identifier as stored within the decentralized databasethen process 1400 moves to 1425 and the result associated with theverification request is invalidated as there may have been a maliciousaltering of the encrypted second dataset.

If the first hash value does equal the unique identifier as storedwithin the decentralized database then process 1400 moves to 1430 andthe system receives, from the user associated with the second key, adecryption key. Once it has been determined that the encrypted seconddataset has not been modified, the system may decrypt the encryptedsecond dataset to generate the decrypted second dataset.

At 1435, the system verifies, based on the decrypted second dataset, theresult. The decrypted second dataset may reveal sensor data includingpersonally identifiable information that may be utilized to verify aresult of a user session. For example, a verification request mayrequest the system to verify that a particular user removed 2 particularitems from a particular area. A merchant may control access to anencrypted first dataset that shows a person removing the 2 particularitems from the particular area. However, because personally identifiableinformation is removed from the first dataset it may not be possible toidentify the person that removed the 2 particular items. On the otherhand, the second dataset may contain personally identifiable informationthat is missing from the first dataset. Thus, the second dataset may beutilized to confirm the identity of the person removing the 2 particularitems from the particular area. However, because a user may controlaccess to the second dataset (via an encryption key) the system mayfirst check that the second dataset has not been altered by utilizing aunique identifier that has been previously stored in a decentralizeddatabase. Thus, process 1400 allows results from a user session to beverified, while allowing a user to control his own personallyidentifiable information, while also preventing the user frommaliciously modifying sensor data containing his own personallyidentifiable information for malicious gain. Although process 1400 hasbeen described utilizing the second dataset any aspect of a user session(e.g., AIDC, exit time, entry time, etc.) may utilized to verify aresult or any other aspect of a user session.

In one embodiment, an oracle or a reviewer may perform one or moreoperations of block 1435. For example, an oracle or reviewer may be usedto verify a result based on one or more data points (e.g., the decryptedsecond dataset). In one embodiment, there may be multiple oracles thatmay need to reach consensus on the verification of a result based on oneor more data points. For example if 2 out of 3 oracles verify a resultthen the result is verified. The oracle(s) may be compensated (e.g. by adigital asset) for performing the verification process. The amount ofcompensation may be based on the accuracy and/or timeliness of theverification. For example, if an oracle verifies a result within a fewminutes after the oracle receives a verification request, then theoracle may be compensated more than if the oracle verifies the sameresult within a few hours after the oracle has received the verificationrequest. An oracle's compensation may be tied to other factors, such asthe amount of sensor data (or other data points) that must be utilizedto verify a transaction. In one embodiment, when there are multipleoracles each oracle may verify a result based on a different data point.For example, a first oracle may verify a result based on a decryptedsecond dataset. However, another oracle may verify the same result basedon decrypted AIDC data associated with the same user session. In such anexample, the multiple oracles may come to consensus (e.g., simplemajority, super majority, etc.) on a result in order to verify a resultby different data points. In one embodiment, multiple oracles may eachverify a result based on a variation of the same data point. Forexample, a first oracle may verify a result based on first sensor datawithin a decrypted second dataset. However, another oracle may verifythe same result based on second sensor data within the decrypted seconddataset. In such an example, the first sensor data may indicate videodata from a first camera and/or video data at a first time and thesecond sensor data may indicate video data from a second camera and/orvideo data at a second time. The first and second cameras may bepositioned at different locations and provide different viewing angleswithin an area.

In one embodiment, a group of oracle or reviewers may be implemented byremote connected computing devices. The oracle may verify a result basedon various machine specific techniques. For example, an oracle mayverify a result based on a decrypted second dataset, by performingfacial recognition to identify a user and object recognition to detectobjects removed from an area.

What is claimed is:
 1. A system for a mechanized store having one ormore displays in an area and a plurality of items at the one or moredisplays, the system comprising: one or more sensors configured toidentify one or more items of the plurality of items; one or morecameras configured to detect identities of the one or more items removedby a user from the one or more displays; and one or more processorsconfigured to: receive identities of the one or more items identified bythe one or more sensors; receive identities of the one or more itemsdetected by the one or more cameras; compare the identities of the oneor more items identified by the one or more sensors to the identities ofthe one or more items detected by the one or more cameras to obtain aresult; and save the result to a record of the user.
 2. The system ofclaim 1, wherein the one or more sensors comprise an RFID (RadioFrequency Identification) tag reader.
 3. The system of claim 1, whereinthe one or more sensors comprise an optical scanner.
 4. The system ofclaim 1, wherein the one or more sensors comprise an image sensor. 5.The system of claim 1, wherein the processors are configured to identifythe user based on images from the one or more cameras.
 6. The system ofclaim 1, wherein a structure is configured to permit only one user at atime access to the area.
 7. The system of claim 1, wherein the area is avolume less than 3.5 meters wide by 3.5 meters long by 3.5 meters tall.8. The system of claim 1, wherein the one or more cameras are configuredto detect an identity of an item of the one or more items by identifyingmovement of a hand and determining if the hand is holding the item ofthe one or more items.
 9. The system of claim 1, further comprising awireless receiver configured to unlock doors of a structure based on areceived signal from a device of the user.
 10. The system of claim 1,wherein the processors are configured to identify the user based onimages from the one or more cameras prior to a start of a user session.11. The system of claim 1, wherein: the one or more processors areconfigured to update a first electronic basket and a second electronicbasket; the first electronic basket corresponds to the one or more itemsidentified by the one or more sensors; and the second electronic basketcorresponds to the one or more items removed by the user detected by theone or more cameras.
 12. A method for operating a mechanized store, themethod comprising: permitting a user access to an area, the area havinga plurality of items at one or more displays in the area; identifyingone or more items of the plurality of items using one or more sensors;detecting the identity of the one or more items removed by the user fromthe one or more displays using one or more cameras; comparing identitiesof the one or more items identified by the one or more sensors toidentities of the one or more items detected by the one or more camerasto obtain a result; and saving the result to a record of the user. 13.The method of claim 12, further comprising transmitting the result to amobile device of the user.
 14. The method of claim 12, furthercomprising alerting a store owner, a store employee, an independentcontractor, and/or law enforcement based on the result.
 15. The methodof claim 12, further comprising tracking the user in the area.
 16. Themethod of claim 12, further comprising initiating a credit cardtransaction on a credit card associated with an account of the user,such that the user is charged for the one or more items removed.
 17. Oneor more memory devices comprising instructions that, when executed,cause one or more processors to perform the following steps: permittinga user access to an area, the area having a plurality of items at one ormore displays in the area; identifying one or more items of theplurality of items using one or more sensors; detecting the identity ofthe one or more items removed by the user from the one or more displaysusing one or more cameras; comparing identities of the one or more itemsidentified by the one or more sensors to identities of the one or moreitems detected by the one or more cameras to obtain a result; and savingthe result to a record of the user.
 18. The one or more memory devicesof claim 17, wherein the instructions, when executed, further cause theone or more processors to perform the following steps: identifying adiscrepancy between the identities of the one or more items identifiedby the one or more sensors and the identities of the one or more itemsdetected by the one or more cameras; and determining that thediscrepancy falls within a certain monetary value range.
 19. The one ormore memory devices of claim 17, wherein the one or more sensorscomprise an image sensor.
 20. The one or more memory devices of claim17, wherein the instructions, when executed, further cause the one ormore processors to perform the following step: transmitting the resultto a mobile device of the user.